Release 10.1A: OpenEdge Development:
Web Services

Using object IDs in a SOAP message

This is a sample header of a SOAP message containing an object ID for the object specified in the sample WSDL, using the WSDL-defined <OrderInfoID> SOAP element:

SOAP header containing an object ID

<soap:Header>    <t:OrderInfoID xmlns:t="urn:OrderSvc:OrderInfo"       soap:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/>          <UUID xsi:type="xsd:string">2e62cab6b81150d5:167f64e:f295e997b0:          -8000;<OrderInfo|PX-000001|AO>;M/IryPm3piDcF/W5DsH4GA==</UUID>    </t:OrderInfoID> </soap:Header>

The value of the object ID appears in bold, contained by the <UUID> element.

The same basic <OrderInfoID> element contains the object ID in the SOAP response header that initially returns the OrderInfoID object ID, when the object is created, and is required in any subsequent SOAP request header sent by methods invoked on the OrderInfo object.

Thus, for all Web service objects that require object IDs, your client application must parse out the object ID value in the <UUID> element contained by the object ID element (<OrderInfoID> in the example) and returned in the SOAP response header at object creation, whether it happens automatically or you must program it explicitly. Similarly, for every SOAP request sent by a method invoked on this same object, your client application must create an object ID element containing a <UUID> element that holds this identical object ID value in the SOAP header of the request message.